I have the same problem. My phone is also an iPhone Xr. iOS 17.0.2 Xcode 15.0 Manual Codesigning Provision Profile is selected iPhone is connect with a cable Build and Run from Xcode on the iPhone works Build and install via Xcode Cloud and TestFlight is working But when I want to debug with instruments on the iPhone I am getting the same error message. There is also no selection on the VPN & Device Management screen.

Thank you very much for this code snippet. I watched the session video but it was not clear for me that scrollPosition modifier together with the scrollTargetLayout keep also the relative scrollview position when you add or delete items. This is exactly what I needed. Many thumbs up for this change in iOS 17.

Ok if there is no new setting in Xcode for giving access to third party drivers then the problem must be somewhere else. I am already in contact with the vendor.

Same problem. After I installed macOS 11.0 beta (20A5395g) and Xcode 12.2 beta 3 (12B5035g) all my mac projects are crashing with the same error message. The symbolic breakpoint mentioned above by aussiebloke solves the problem.

I would also like to know if there is a SwiftUI solution for this.

TextField on macOS needs a label and not only a placeholder (all label in forms on macOS should auto align) Sliders and Labels on macOS seems to have a wrong vertical alignment TouchBar is linked to the control that has the focus. More often it makes sense to show the TouchBar when the window appears or the app launches Missing alignment guide for SwiftUI controls having labels. You can either have the leading, trailing or center but not the position behind the label where the control starts The layout of SwiftUI elements on macOS have still some issues

I also hope we will see a SwiftUI solution for this problem before the end of the beta

I found a similar discussion for this problem in the internet. But to be honest the solution they provide looks more like an ugly workaround. Instead using an array of observable items they are using unique ids for each list item and store them into a dictionary. Then they have another array with the keys. In the SwiftUI list they are iterating with ForEach over the keys and pass the dictionary items to the list view. The dictionary item is then used for the detail view. This works but to be honest I hope someone has a better solution for this very common problem. In my application I have a sidebar with a list of items containing an image/name/subtitle and a detailed view for changing these values. After leaving the details view the changes are stored correctly in the array. But the publisher for the list does not inform the SwiftUI view that it has to update the list.

We are now in development. Can this also happen after we released our app? In my opinion I did something wrong with the NavigationView and frame modifier. After this the sidebar was collapsed. But if this happen also in the release version even the code is correct the users cannot delete the container folder.

Seems I have the same problem. First both sidebar and detail view were visible. Once the sidebar is collapsed there is no way to bring it back. Any ideas to solve this in code?

Thank you, thats exactly what I need.

It seems that the commit() causes the memory increase. The MTLCommandQueue makeCommandBuffer call is not the problem. Only when you commit your command buffer you will the memory usage going up. autoreleasepool{} does not make a difference. Maybe it is not a bug but data stored in memory for debugging with Xcode.